Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a7f2f35e764e1cd71058c0f148d3c2a1875283be53521c14d291da3ef366703

Tx prefix hash: 0cef8547bf1357fa2d658558384fa7b7eb1c3f8c2b986a90fb08a3a47b3be680
Tx public key: 3ba1a5e292ae12023e8230efa1b247fefc13b9d3524e58caf361e71e145558b5
Timestamp: 1711669108 Timestamp [UCT]: 2024-03-28 23:38:28 Age [y:d:h:m:s]: 01:012:17:32:56
Block: 988507 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 270043 RingCT/type: yes/0
Extra: 013ba1a5e292ae12023e8230efa1b247fefc13b9d3524e58caf361e71e145558b502110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b3dc9274897e69c5af8d4004f8c47626a0761c57b39aab6c83ff5a3154f118d7 0.600000000000 1448786 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": 988517, "vin": [ { "gen": { "height": 988507 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b3dc9274897e69c5af8d4004f8c47626a0761c57b39aab6c83ff5a3154f118d7" } } ], "extra": [ 1, 59, 161, 165, 226, 146, 174, 18, 2, 62, 130, 48, 239, 161, 178, 71, 254, 252, 19, 185, 211, 82, 78, 88, 202, 243, 97, 231, 30, 20, 85, 88, 181, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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