Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: b26e1b5e1f0520b31784d2db140695408e7c4b0f8f92aa9d7314d667f3f48619

Tx prefix hash: 1b318657913935e826488cf8a042aa3579bc259ca2664ad273a82bca2a464118
Tx public key: ec6fb7b570c40e7b3180923bf9033c2515e6ac64a5ce626f3ac01e201f3f2c44
Timestamp: 1632297837 Timestamp [UCT]: 2021-09-22 08:03:57 Age [y:d:h:m:s]: 03:166:04:13:32
Block: 338660 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 894724 RingCT/type: yes/0
Extra: 01ec6fb7b570c40e7b3180923bf9033c2515e6ac64a5ce626f3ac01e201f3f2c4402110000003ff60c5d7e000000000000000000

1 output(s) for total of 46.331810315000 dcy

stealth address amount amount idx
00: b6bf7e8f942b7db0fad072ae405c4b431779c2b1d19e7f2d12e7323be766ccc9 46.331810315000 696887 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 338670, "vin": [ { "gen": { "height": 338660 } } ], "vout": [ { "amount": 46331810315, "target": { "key": "b6bf7e8f942b7db0fad072ae405c4b431779c2b1d19e7f2d12e7323be766ccc9" } } ], "extra": [ 1, 236, 111, 183, 181, 112, 196, 14, 123, 49, 128, 146, 59, 249, 3, 60, 37, 21, 230, 172, 100, 165, 206, 98, 111, 58, 192, 30, 32, 31, 63, 44, 68, 2, 17, 0, 0, 0, 63, 246, 12, 93, 126, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8