Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a7dbea1110106bc664b330512b2461dd51391a6625f89262c72bc65af09b9aa

Tx prefix hash: 31789e21ac5436c30624a0dc634bc1fb856ea083068a2c47fb79fdf64bcbc3a3
Tx public key: aa9de74f9dfe3d1b499c667d5194f4d7e5ce63fa0df422c5c92ab572a853f7b6
Timestamp: 1699704452 Timestamp [UCT]: 2023-11-11 12:07:32 Age [y:d:h:m:s]: 01:139:07:51:59
Block: 889305 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360753 RingCT/type: yes/0
Extra: 01aa9de74f9dfe3d1b499c667d5194f4d7e5ce63fa0df422c5c92ab572a853f7b602110000000675e3f0e9000000000000000000

1 output(s) for total of 0.694006225000 dcy

stealth address amount amount idx
00: 8df97877abacf7589610b0d053988f5dcbf7f7ee76710d0495509051e57ccb7c 0.694006225000 1345290 of 0

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": 889315, "vin": [ { "gen": { "height": 889305 } } ], "vout": [ { "amount": 694006225, "target": { "key": "8df97877abacf7589610b0d053988f5dcbf7f7ee76710d0495509051e57ccb7c" } } ], "extra": [ 1, 170, 157, 231, 79, 157, 254, 61, 27, 73, 156, 102, 125, 81, 148, 244, 215, 229, 206, 99, 250, 13, 244, 34, 197, 201, 42, 181, 114, 168, 83, 247, 182, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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