Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad55941cf91afab3d4f8533978a13c136d307bc9d44179724b26f55a8aba55b5

Tx prefix hash: 388e69f0237decf0f1dd40c886c11f3f3f404e4954b96934954d3477f54ae379
Tx public key: 308dd202c51ce00bd7cfee851c522809624c09a89f4469fbf8e76a1c3c78516f
Timestamp: 1728211591 Timestamp [UCT]: 2024-10-06 10:46:31 Age [y:d:h:m:s]: 00:177:14:44:08
Block: 1125642 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 126710 RingCT/type: yes/0
Extra: 01308dd202c51ce00bd7cfee851c522809624c09a89f4469fbf8e76a1c3c78516f02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a241441e8c9d7eb4e3db9d0bb0dc12ef3617ad922b054e06aa02a7be703563b 0.600000000000 1608393 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": 1125652, "vin": [ { "gen": { "height": 1125642 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a241441e8c9d7eb4e3db9d0bb0dc12ef3617ad922b054e06aa02a7be703563b" } } ], "extra": [ 1, 48, 141, 210, 2, 197, 28, 224, 11, 215, 207, 238, 133, 28, 82, 40, 9, 98, 76, 9, 168, 159, 68, 105, 251, 248, 231, 106, 28, 60, 120, 81, 111, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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