Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d68c8f4ff135e47ef1ee2862aa5da6b13d01e627cc94c6144ddef4cb6651e775

Tx prefix hash: 9252469b5c558c61ecd46e4117efc8470ed255b59a25ab18f2fcb31769bfb177
Tx public key: 594904e2329fa828b88b6b79a12d5dbb21fcafd9a12b04747807b3ea4d23e979
Timestamp: 1705156381 Timestamp [UCT]: 2024-01-13 14:33:01 Age [y:d:h:m:s]: 00:320:05:33:57
Block: 934484 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229291 RingCT/type: yes/0
Extra: 01594904e2329fa828b88b6b79a12d5dbb21fcafd9a12b04747807b3ea4d23e9790211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a66e20fe72d83d105b35cb375f6ed525a1c8f1550e4d540c061581cd5ebd97b6 0.600000000000 1392496 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": 934494, "vin": [ { "gen": { "height": 934484 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a66e20fe72d83d105b35cb375f6ed525a1c8f1550e4d540c061581cd5ebd97b6" } } ], "extra": [ 1, 89, 73, 4, 226, 50, 159, 168, 40, 184, 139, 107, 121, 161, 45, 93, 187, 33, 252, 175, 217, 161, 43, 4, 116, 120, 7, 179, 234, 77, 35, 233, 121, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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