Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d227fb588e8c1984e8d19ebb6a3fdf9a55de86f94a981f92f62ab321c4692656

Tx prefix hash: 6d2b84acc224cce020451a1c618daafb78e6a284d1b1b932d786013046023081
Tx public key: 8b576fea75bc2b3c97b4ed57feb03520b16d5d55b9b78234f3a29121dbed3956
Timestamp: 1724758881 Timestamp [UCT]: 2024-08-27 11:41:21 Age [y:d:h:m:s]: 00:292:01:19:06
Block: 1097001 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208541 RingCT/type: yes/0
Extra: 018b576fea75bc2b3c97b4ed57feb03520b16d5d55b9b78234f3a29121dbed395602110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b93376103b05598d1dcb6ba06c03b0036bc5e6565cef59d946eb3772c5007228 0.600000000000 1572264 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": 1097011, "vin": [ { "gen": { "height": 1097001 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b93376103b05598d1dcb6ba06c03b0036bc5e6565cef59d946eb3772c5007228" } } ], "extra": [ 1, 139, 87, 111, 234, 117, 188, 43, 60, 151, 180, 237, 87, 254, 176, 53, 32, 177, 109, 93, 85, 185, 183, 130, 52, 243, 162, 145, 33, 219, 237, 57, 86, 2, 17, 0, 0, 0, 10, 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