Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b2382807f845907e6dbf3811f5db75d9e4e7f7c4bd475eb6ff941d3e6178c1c

Tx prefix hash: 5f6ca2cc3a521e8f6327a9648dbcccd217cad038be99e83ff7342aadf508b463
Tx public key: 712002e187ed545e9a445caba29fd5f3515e55668e7e43e7056032941ba88f1d
Timestamp: 1726499098 Timestamp [UCT]: 2024-09-16 15:04:58 Age [y:d:h:m:s]: 00:058:17:37:59
Block: 1111440 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41972 RingCT/type: yes/0
Extra: 01712002e187ed545e9a445caba29fd5f3515e55668e7e43e7056032941ba88f1d021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d3dd551e33f6de3832a9f642cdd30cd5785c8f631d4f6da6891ff3a2af1a76e 0.600000000000 1590397 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": 1111450, "vin": [ { "gen": { "height": 1111440 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d3dd551e33f6de3832a9f642cdd30cd5785c8f631d4f6da6891ff3a2af1a76e" } } ], "extra": [ 1, 113, 32, 2, 225, 135, 237, 84, 94, 154, 68, 92, 171, 162, 159, 213, 243, 81, 94, 85, 102, 142, 126, 67, 231, 5, 96, 50, 148, 27, 168, 143, 29, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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