Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06480fb3f9ebe8cb84bf6adcb5c975372717017b7ae322f2b755b4a4cdae9418

Tx prefix hash: 76535b5cf2d001d2563564851bc0f0d2290e99e4713d9ecd3ea33481930cf4f1
Tx public key: ba64e50d798e1d4521ab2b25829c527524c11dcd432204afc97ee81e0c143f8d
Timestamp: 1724551638 Timestamp [UCT]: 2024-08-25 02:07:18 Age [y:d:h:m:s]: 00:294:06:13:33
Block: 1095314 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210100 RingCT/type: yes/0
Extra: 01ba64e50d798e1d4521ab2b25829c527524c11dcd432204afc97ee81e0c143f8d021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d40b8d8c7ca18e76f3b0392d79d2271870b2e8ded268df2d0e1262914ce3bab9 0.600000000000 1570475 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": 1095324, "vin": [ { "gen": { "height": 1095314 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d40b8d8c7ca18e76f3b0392d79d2271870b2e8ded268df2d0e1262914ce3bab9" } } ], "extra": [ 1, 186, 100, 229, 13, 121, 142, 29, 69, 33, 171, 43, 37, 130, 156, 82, 117, 36, 193, 29, 205, 67, 34, 4, 175, 201, 126, 232, 30, 12, 20, 63, 141, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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