Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 19bc5df649ae8f1ce2e8f21f98808943dabd14a56c121ff9ee80676c2e297883

Tx prefix hash: b8ac2abdde411263fbc30cd507e7ae5baddb2d9d30b208de303356a8051de259
Tx public key: ee890e4a9de7981b85a8e4ccef95d8e5e9781718cc2d7cae0589de0c59c0a185
Timestamp: 1728200602 Timestamp [UCT]: 2024-10-06 07:43:22 Age [y:d:h:m:s]: 00:250:20:30:36
Block: 1125545 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179040 RingCT/type: yes/0
Extra: 01ee890e4a9de7981b85a8e4ccef95d8e5e9781718cc2d7cae0589de0c59c0a18502110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eec619dc8fc474e59f1f291952aa8689e31f18a438a14354b3b34728f40cf209 0.600000000000 1608296 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": 1125555, "vin": [ { "gen": { "height": 1125545 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eec619dc8fc474e59f1f291952aa8689e31f18a438a14354b3b34728f40cf209" } } ], "extra": [ 1, 238, 137, 14, 74, 157, 231, 152, 27, 133, 168, 228, 204, 239, 149, 216, 229, 233, 120, 23, 24, 204, 45, 124, 174, 5, 137, 222, 12, 89, 192, 161, 133, 2, 17, 0, 0, 0, 2, 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