Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2668c1cd34a8c1738fe378f2db107065e4d2b95400075d1e45da11f0a4e34f2e

Tx prefix hash: ffb66621d519f46fc2bf7b7278e6d17a15a451e378c548859436ef3985bb4709
Tx public key: 0a01b1893ef36d23d8645563de93582e5b44274b2e3d0e99cc35cb742a6818fe
Timestamp: 1722395704 Timestamp [UCT]: 2024-07-31 03:15:04 Age [y:d:h:m:s]: 00:267:09:28:50
Block: 1077409 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191030 RingCT/type: yes/0
Extra: 010a01b1893ef36d23d8645563de93582e5b44274b2e3d0e99cc35cb742a6818fe02110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e9fabf244c9275a699e31d2d4c0ff9b813b2264b30fe0e48c98803b5a0765f5 0.600000000000 1549956 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": 1077419, "vin": [ { "gen": { "height": 1077409 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e9fabf244c9275a699e31d2d4c0ff9b813b2264b30fe0e48c98803b5a0765f5" } } ], "extra": [ 1, 10, 1, 177, 137, 62, 243, 109, 35, 216, 100, 85, 99, 222, 147, 88, 46, 91, 68, 39, 75, 46, 61, 14, 153, 204, 53, 203, 116, 42, 104, 24, 254, 2, 17, 0, 0, 0, 8, 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