Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ddad04f77d1fef9f7b59882d03813ec193b23b8051a2f7357d75e96c9b6f1ca

Tx prefix hash: ccc3c67fa2fc909e7ce7b1cc854fe61acc8e92bf5cde7719b96333093f02fe76
Tx public key: 594fa972150131147d42ac9eb6e57c8e7d5ddfdfeea06d2908de54fe788825d8
Timestamp: 1708455607 Timestamp [UCT]: 2024-02-20 19:00:07 Age [y:d:h:m:s]: 01:025:16:39:13
Block: 961849 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279400 RingCT/type: yes/0
Extra: 01594fa972150131147d42ac9eb6e57c8e7d5ddfdfeea06d2908de54fe788825d802110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bfd0f89461abbd22f1f1c6f9e838b541dc2d9bef2779e8b0c50215e7d0632783 0.600000000000 1421462 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": 961859, "vin": [ { "gen": { "height": 961849 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bfd0f89461abbd22f1f1c6f9e838b541dc2d9bef2779e8b0c50215e7d0632783" } } ], "extra": [ 1, 89, 79, 169, 114, 21, 1, 49, 20, 125, 66, 172, 158, 182, 229, 124, 142, 125, 93, 223, 223, 238, 160, 109, 41, 8, 222, 84, 254, 120, 136, 37, 216, 2, 17, 0, 0, 0, 1, 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