Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 67cfe7666965a1173f007c5575b7f2225694380c56053901690dd3a85d3d2424

Tx prefix hash: 2059e09285c05941fccb2abedce724f90d1f9bf3bc948063f8526d2d6bc61781
Tx public key: ca84d3fe5b7a0263b5be169a446ff3f6263ffa464e2de79e3b1c98b38dcb41fb
Timestamp: 1716410345 Timestamp [UCT]: 2024-05-22 20:39:05 Age [y:d:h:m:s]: 00:298:14:43:14
Block: 1027792 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213451 RingCT/type: yes/0
Extra: 01ca84d3fe5b7a0263b5be169a446ff3f6263ffa464e2de79e3b1c98b38dcb41fb02110000000f52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 507a9a337be660c60c95707f7f2c0e836013dc5ea51dd87e6d3f9904b4b16e80 0.600000000000 1495605 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": 1027802, "vin": [ { "gen": { "height": 1027792 } } ], "vout": [ { "amount": 600000000, "target": { "key": "507a9a337be660c60c95707f7f2c0e836013dc5ea51dd87e6d3f9904b4b16e80" } } ], "extra": [ 1, 202, 132, 211, 254, 91, 122, 2, 99, 181, 190, 22, 154, 68, 111, 243, 246, 38, 63, 250, 70, 78, 45, 231, 158, 59, 28, 152, 179, 141, 203, 65, 251, 2, 17, 0, 0, 0, 15, 82, 212, 126, 148, 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