Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a1c4a47e84c375e725243b2b1a21529430e85b17f57cff0a1d52ce3d71b67c1

Tx prefix hash: e9b73e097647e9c782cab4bd91063dd06105947da1f6bc99b3ea607323e18b34
Tx public key: 9b0b94d0f325153e3a3f7c556a4bfc7bb848cafd038a9b8ff8d5f14d2274148d
Timestamp: 1732072366 Timestamp [UCT]: 2024-11-20 03:12:46 Age [y:d:h:m:s]: 00:138:08:36:09
Block: 1157540 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98703 RingCT/type: yes/0
Extra: 019b0b94d0f325153e3a3f7c556a4bfc7bb848cafd038a9b8ff8d5f14d2274148d0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2e734c1542d9a55e61e902d277f59ecaed8bcbd0c4dac889b437ebf202b806e1 0.600000000000 1643163 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": 1157550, "vin": [ { "gen": { "height": 1157540 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2e734c1542d9a55e61e902d277f59ecaed8bcbd0c4dac889b437ebf202b806e1" } } ], "extra": [ 1, 155, 11, 148, 208, 243, 37, 21, 62, 58, 63, 124, 85, 106, 75, 252, 123, 184, 72, 202, 253, 3, 138, 155, 143, 248, 213, 241, 77, 34, 116, 20, 141, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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