Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28f77d8e3278d65009a16a76fe131d6530afb3cb521e6eadbafaf14b21dda918

Tx prefix hash: 43501c47ea89933330f1bac40366fe500a24a3e04d487ce12fd1abc48b4a1a3e
Tx public key: 2dfadab0a7a91cf8da53440daddca8e5b7dbece80f1f07cb0303794c185a07e4
Timestamp: 1632956720 Timestamp [UCT]: 2021-09-29 23:05:20 Age [y:d:h:m:s]: 03:131:17:03:07
Block: 343465 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 870725 RingCT/type: yes/0
Extra: 012dfadab0a7a91cf8da53440daddca8e5b7dbece80f1f07cb0303794c185a07e402110000000c36fe6557000000000000000000

1 output(s) for total of 44.664071033000 dcy

stealth address amount amount idx
00: 87b4ed4f7130dfe6d48fec7389c0205d21d4ac5c1107e8eb52b00005b9243549 44.664071033000 705018 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": 343475, "vin": [ { "gen": { "height": 343465 } } ], "vout": [ { "amount": 44664071033, "target": { "key": "87b4ed4f7130dfe6d48fec7389c0205d21d4ac5c1107e8eb52b00005b9243549" } } ], "extra": [ 1, 45, 250, 218, 176, 167, 169, 28, 248, 218, 83, 68, 13, 173, 220, 168, 229, 183, 219, 236, 232, 15, 31, 7, 203, 3, 3, 121, 76, 24, 90, 7, 228, 2, 17, 0, 0, 0, 12, 54, 254, 101, 87, 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