Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 09c6bd72d00fc192ef8f890b489712695863d865ab6f74433b6342c8f8951a49

Tx prefix hash: bb2173470514586018254f9d4e229a7e11492e7eb9fd0aa81a0b210fc3844e66
Tx public key: ef33ee8c8eaf05e28c79dcf9073a79ca9958a01218c3df12fceeb39faaf08f8a
Timestamp: 1701125858 Timestamp [UCT]: 2023-11-27 22:57:38 Age [y:d:h:m:s]: 01:137:12:27:20
Block: 901080 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 359452 RingCT/type: yes/0
Extra: 01ef33ee8c8eaf05e28c79dcf9073a79ca9958a01218c3df12fceeb39faaf08f8a0211000000044b8f5122000000000000000000

1 output(s) for total of 0.634377667000 dcy

stealth address amount amount idx
00: 82d3d8556c6753576ffc986e83de5e8f92627f33e72c86412c512b5aa035e1aa 0.634377667000 1357611 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": 901090, "vin": [ { "gen": { "height": 901080 } } ], "vout": [ { "amount": 634377667, "target": { "key": "82d3d8556c6753576ffc986e83de5e8f92627f33e72c86412c512b5aa035e1aa" } } ], "extra": [ 1, 239, 51, 238, 140, 142, 175, 5, 226, 140, 121, 220, 249, 7, 58, 121, 202, 153, 88, 160, 18, 24, 195, 223, 18, 252, 238, 179, 159, 170, 240, 143, 138, 2, 17, 0, 0, 0, 4, 75, 143, 81, 34, 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