Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3a05fd33a3d12b38803f847146a958b81e320ea34df326cc6c539d7fadb837b

Tx prefix hash: 00a6aaecf01d0747e91e5127dfda1f190d7fa13edf444cfe449c11a1cdc47cf6
Tx public key: c1f2a969ced574912846b762b11e2667bb7d658b83f9f235116dcae2f407f1e4
Timestamp: 1709576455 Timestamp [UCT]: 2024-03-04 18:20:55 Age [y:d:h:m:s]: 01:030:08:01:08
Block: 971143 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282670 RingCT/type: yes/0
Extra: 01c1f2a969ced574912846b762b11e2667bb7d658b83f9f235116dcae2f407f1e40211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 557ac71b51795e6491b8300f3e0d156a8a29dd02ba87ac957051d321b02a11bf 0.600000000000 1431028 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": 971153, "vin": [ { "gen": { "height": 971143 } } ], "vout": [ { "amount": 600000000, "target": { "key": "557ac71b51795e6491b8300f3e0d156a8a29dd02ba87ac957051d321b02a11bf" } } ], "extra": [ 1, 193, 242, 169, 105, 206, 213, 116, 145, 40, 70, 183, 98, 177, 30, 38, 103, 187, 125, 101, 139, 131, 249, 242, 53, 17, 109, 202, 226, 244, 7, 241, 228, 2, 17, 0, 0, 0, 3, 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