Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5136909f27f76308c823aa573695255306385dfb92afaab8d06077808a55269

Tx prefix hash: 8a06cd1e9c0bf1c25a3f20df015b3b12649f7cbcd4280e035ff23f9265e52816
Tx public key: 64bb0717637bcae1a3a029bc1b40733cf4f74194206dd5e21d124b2b9faa7bc5
Timestamp: 1735424539 Timestamp [UCT]: 2024-12-28 22:22:19 Age [y:d:h:m:s]: 00:172:07:52:15
Block: 1185304 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122849 RingCT/type: yes/0
Extra: 0164bb0717637bcae1a3a029bc1b40733cf4f74194206dd5e21d124b2b9faa7bc50211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e043cec0df43078fc2d7c91f3ff77c8cde14e0095e91e66ae0937d0e119390e8 0.600000000000 1671771 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": 1185314, "vin": [ { "gen": { "height": 1185304 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e043cec0df43078fc2d7c91f3ff77c8cde14e0095e91e66ae0937d0e119390e8" } } ], "extra": [ 1, 100, 187, 7, 23, 99, 123, 202, 225, 163, 160, 41, 188, 27, 64, 115, 60, 244, 247, 65, 148, 32, 109, 213, 226, 29, 18, 75, 43, 159, 170, 123, 197, 2, 17, 0, 0, 0, 2, 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