Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ae7084433d0ea7b2846e51dd177efde5d07e8949931332dabf427768609a594

Tx prefix hash: f77acbdb67c1ec5579ebeb398f937ce7892b8d2e77b75f7773c05cff016577b7
Tx public key: 90873f5bbd0c32c45bb1c4c90284dac4beb9ecffe0e5f1afd556959e34ce3ca5
Timestamp: 1702435799 Timestamp [UCT]: 2023-12-13 02:49:59 Age [y:d:h:m:s]: 01:133:22:44:13
Block: 911958 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356863 RingCT/type: yes/0
Extra: 0190873f5bbd0c32c45bb1c4c90284dac4beb9ecffe0e5f1afd556959e34ce3ca502110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 822080cddb4a20f45131db9d759e1959858629b6b5a31729241021ef2bb082c5 0.600000000000 1369176 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": 911968, "vin": [ { "gen": { "height": 911958 } } ], "vout": [ { "amount": 600000000, "target": { "key": "822080cddb4a20f45131db9d759e1959858629b6b5a31729241021ef2bb082c5" } } ], "extra": [ 1, 144, 135, 63, 91, 189, 12, 50, 196, 91, 177, 196, 201, 2, 132, 218, 196, 190, 185, 236, 255, 224, 229, 241, 175, 213, 86, 149, 158, 52, 206, 60, 165, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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