Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4645cb4ed8e00941900a1244db4b505936dadbb1a16b4ce50e12660f8790a5ce

Tx prefix hash: fd3319d7eaa75510863d9792da076dc127f95a252f85f2ec72a55d6e145095e7
Tx public key: 0272e716d13f5530aa782ddf5f7bd613046bb6a8f57fdedd3e4e67d11a41dd48
Timestamp: 1738653322 Timestamp [UCT]: 2025-02-04 07:15:22 Age [y:d:h:m:s]: 00:274:18:34:41
Block: 1211765 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194116 RingCT/type: yes/0
Extra: 010272e716d13f5530aa782ddf5f7bd613046bb6a8f57fdedd3e4e67d11a41dd48021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d16b988a35e99d04b80838c04c62b23cba9d88b5e13fae340623a01272c5c582 0.600000000000 1698528 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": 1211775, "vin": [ { "gen": { "height": 1211765 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d16b988a35e99d04b80838c04c62b23cba9d88b5e13fae340623a01272c5c582" } } ], "extra": [ 1, 2, 114, 231, 22, 209, 63, 85, 48, 170, 120, 45, 223, 95, 123, 214, 19, 4, 107, 182, 168, 245, 127, 222, 221, 62, 78, 103, 209, 26, 65, 221, 72, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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