Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a180aff6f55f6c58cbc73e1feee5a0230be336346038777ada5b9a966b397283

Tx prefix hash: 50dde4075a69791da15351e6f8111e157afe86b7e7a36304c2db7216de674eb7
Tx public key: 1a05a2dce11523ae2b433e7c1d245e44cfe7847e0f0e8f866dec3d52b950779e
Timestamp: 1703567237 Timestamp [UCT]: 2023-12-26 05:07:17 Age [y:d:h:m:s]: 01:172:13:26:00
Block: 921318 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 384391 RingCT/type: yes/0
Extra: 011a05a2dce11523ae2b433e7c1d245e44cfe7847e0f0e8f866dec3d52b950779e0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a43f1ac39994b7c64b335dc901beabcfb951b2cc18534bdbcb6e88759eee322 0.600000000000 1379004 of 15

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": 921328, "vin": [ { "gen": { "height": 921318 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a43f1ac39994b7c64b335dc901beabcfb951b2cc18534bdbcb6e88759eee322" } } ], "extra": [ 1, 26, 5, 162, 220, 225, 21, 35, 174, 43, 67, 62, 124, 29, 36, 94, 68, 207, 231, 132, 126, 15, 14, 143, 134, 109, 236, 61, 82, 185, 80, 119, 158, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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