Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f97c6a33ddf09113cb9f03b58aeb4f5356d987e100cee05de45dfb8e7d79ce00

Tx prefix hash: f3e09d0089ae1b7d550d57e05dfb453969452da33b9d64b939df55cc0d26e1e0
Tx public key: e7e294e43c0d1169e918a2f057422c4490a9b9f6e4bcb2ee1e470a8bcc962106
Timestamp: 1722572103 Timestamp [UCT]: 2024-08-02 04:15:03 Age [y:d:h:m:s]: 00:319:13:19:04
Block: 1078879 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 228223 RingCT/type: yes/0
Extra: 01e7e294e43c0d1169e918a2f057422c4490a9b9f6e4bcb2ee1e470a8bcc962106021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d8f4198afc56cace99a360bfee8aaa37ea0b04d9c6877f32c7815a9de4aa20c 0.600000000000 1551594 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": 1078889, "vin": [ { "gen": { "height": 1078879 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d8f4198afc56cace99a360bfee8aaa37ea0b04d9c6877f32c7815a9de4aa20c" } } ], "extra": [ 1, 231, 226, 148, 228, 60, 13, 17, 105, 233, 24, 162, 240, 87, 66, 44, 68, 144, 169, 185, 246, 228, 188, 178, 238, 30, 71, 10, 139, 204, 150, 33, 6, 2, 17, 0, 0, 0, 1, 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