Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3288dcfb12786820e45e4e479222a0b13089a0aa20eb5602986d50f4a56d9d09

Tx prefix hash: 48d0544fab3b667b9c9f11f6e623aeb8f702548f7c7088ac81185a4317124408
Tx public key: f82dcfc5fb3a31f71eae4bcfc1595c3bfdf7a663dabb9602f6c78b7ce38fc06c
Timestamp: 1577623389 Timestamp [UCT]: 2019-12-29 12:43:09 Age [y:d:h:m:s]: 05:066:07:29:52
Block: 34359 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1197105 RingCT/type: yes/0
Extra: 01f82dcfc5fb3a31f71eae4bcfc1595c3bfdf7a663dabb9602f6c78b7ce38fc06c0211000000038a2ee0d9000000000000000000

1 output(s) for total of 472.231796481000 dcy

stealth address amount amount idx
00: 7e01c1d86711a095d05c3024d2d2baa5fd44a98846a21f3e1669f6f4ddb75353 472.231796481000 57800 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": 34369, "vin": [ { "gen": { "height": 34359 } } ], "vout": [ { "amount": 472231796481, "target": { "key": "7e01c1d86711a095d05c3024d2d2baa5fd44a98846a21f3e1669f6f4ddb75353" } } ], "extra": [ 1, 248, 45, 207, 197, 251, 58, 49, 247, 30, 174, 75, 207, 193, 89, 92, 59, 253, 247, 166, 99, 218, 187, 150, 2, 246, 199, 139, 124, 227, 143, 192, 108, 2, 17, 0, 0, 0, 3, 138, 46, 224, 217, 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