Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c257e52f8b9c12347fffa5b1df98ffdc1d0254ecf3322a42699bd2fe42a9c68f

Tx prefix hash: f1a103c4384489734e042991fa34acf1be92ce747ac7aef89ce132a71b3526d7
Tx public key: 06e975893b529215498b7c1d74efc9807a1eba5254a54b2c6050e81d0baf4f2f
Timestamp: 1726520110 Timestamp [UCT]: 2024-09-16 20:55:10 Age [y:d:h:m:s]: 00:159:13:42:28
Block: 1111605 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113838 RingCT/type: yes/0
Extra: 0106e975893b529215498b7c1d74efc9807a1eba5254a54b2c6050e81d0baf4f2f02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4aced9ad53224f6ae5b9ed3b6b499ebc326939583cd5bf0caf17bae673b98d47 0.600000000000 1590626 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": 1111615, "vin": [ { "gen": { "height": 1111605 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4aced9ad53224f6ae5b9ed3b6b499ebc326939583cd5bf0caf17bae673b98d47" } } ], "extra": [ 1, 6, 233, 117, 137, 59, 82, 146, 21, 73, 139, 124, 29, 116, 239, 201, 128, 122, 30, 186, 82, 84, 165, 75, 44, 96, 80, 232, 29, 11, 175, 79, 47, 2, 17, 0, 0, 0, 5, 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