Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d87ef839ccb922bb08ebaef05f74ade1590ee6adf9d161ea683291d0c219c976

Tx prefix hash: 7dcf55cad55166cc37379b803c70d84259ebc1f35994bcde5e8b24685d095f86
Tx public key: 0623043123782d1b84da2877dcb622f8b47b3f4d1cc1308e38f73aea8eecb955
Timestamp: 1681545940 Timestamp [UCT]: 2023-04-15 08:05:40 Age [y:d:h:m:s]: 01:272:09:25:25
Block: 738989 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 456184 RingCT/type: yes/0
Extra: 010623043123782d1b84da2877dcb622f8b47b3f4d1cc1308e38f73aea8eecb9550211000000025029cbac000000000000000000

1 output(s) for total of 2.184856376000 dcy

stealth address amount amount idx
00: b3e9bf19f902660a0fed53e780237dbc36e2d9df3337dfb9dc24388387282ec3 2.184856376000 1185786 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": 738999, "vin": [ { "gen": { "height": 738989 } } ], "vout": [ { "amount": 2184856376, "target": { "key": "b3e9bf19f902660a0fed53e780237dbc36e2d9df3337dfb9dc24388387282ec3" } } ], "extra": [ 1, 6, 35, 4, 49, 35, 120, 45, 27, 132, 218, 40, 119, 220, 182, 34, 248, 180, 123, 63, 77, 28, 193, 48, 142, 56, 247, 58, 234, 142, 236, 185, 85, 2, 17, 0, 0, 0, 2, 80, 41, 203, 172, 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