Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb40d41cf53179dd35bdc754811a4eb7cac2568f4eb7dd5d7032649f74bcba24

Tx prefix hash: eea28de371e31df9bd36e07f0e09c8afb7219ac40cb2b7bd9d05317ee2abf7df
Tx public key: 6b8b8f0d6548d8d7b1a332fedf018edaa904033a63dc311c29dc8f339dc9eb98
Timestamp: 1628706479 Timestamp [UCT]: 2021-08-11 18:27:59 Age [y:d:h:m:s]: 03:135:18:41:10
Block: 311932 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 870247 RingCT/type: yes/0
Extra: 016b8b8f0d6548d8d7b1a332fedf018edaa904033a63dc311c29dc8f339dc9eb9802110000001901f1e57f000000000000000000

1 output(s) for total of 56.812024790000 dcy

stealth address amount amount idx
00: df9d8a4e208f208c1d13d8f14c970904667ca26112879c271d07d81ca7e942ca 56.812024790000 649103 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": 311942, "vin": [ { "gen": { "height": 311932 } } ], "vout": [ { "amount": 56812024790, "target": { "key": "df9d8a4e208f208c1d13d8f14c970904667ca26112879c271d07d81ca7e942ca" } } ], "extra": [ 1, 107, 139, 143, 13, 101, 72, 216, 215, 177, 163, 50, 254, 223, 1, 142, 218, 169, 4, 3, 58, 99, 220, 49, 28, 41, 220, 143, 51, 157, 201, 235, 152, 2, 17, 0, 0, 0, 25, 1, 241, 229, 127, 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