Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a01dc6674b9072ec944096b6108935469c40a3b1e1f734906daeecc0c1b37bc

Tx prefix hash: 4792aca4e0bb7f9d4751a2fc629493847ae4c91a506ceffa3ca025facdb2cf7a
Tx public key: 8dccf32bc09e44211d890e5fd9d6110f7b2b577e45d45227e01cdb0aeb5f088e
Timestamp: 1704959995 Timestamp [UCT]: 2024-01-11 07:59:55 Age [y:d:h:m:s]: 01:124:07:04:04
Block: 932851 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 349976 RingCT/type: yes/0
Extra: 018dccf32bc09e44211d890e5fd9d6110f7b2b577e45d45227e01cdb0aeb5f088e02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 84044bb509ddf33ed776a7774594c060edab79cb659bdd9d1d0d4bb6746aafd6 0.600000000000 1390791 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": 932861, "vin": [ { "gen": { "height": 932851 } } ], "vout": [ { "amount": 600000000, "target": { "key": "84044bb509ddf33ed776a7774594c060edab79cb659bdd9d1d0d4bb6746aafd6" } } ], "extra": [ 1, 141, 204, 243, 43, 192, 158, 68, 33, 29, 137, 14, 95, 217, 214, 17, 15, 123, 43, 87, 126, 69, 212, 82, 39, 224, 28, 219, 10, 235, 95, 8, 142, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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