Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eb34716952e1f41617eaaec1e1542007589cedf81a8aec63f86a0148372c61e3

Tx prefix hash: 4d324413f84453e5af6ea7ebd32dc3db3c5cd5f5f324bc988364978398f90aa3
Tx public key: df4132ea575800b9a2e62d9ec4cecea685db0497abc52f5f9bbb9797c7656d4d
Timestamp: 1736546050 Timestamp [UCT]: 2025-01-10 21:54:10 Age [y:d:h:m:s]: 00:159:22:52:47
Block: 1194589 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114006 RingCT/type: yes/0
Extra: 01df4132ea575800b9a2e62d9ec4cecea685db0497abc52f5f9bbb9797c7656d4d021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 44f8e580277bd6066101a6bb343a79bc9e815d000bf64490c7efba098b9ea732 0.600000000000 1681166 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": 1194599, "vin": [ { "gen": { "height": 1194589 } } ], "vout": [ { "amount": 600000000, "target": { "key": "44f8e580277bd6066101a6bb343a79bc9e815d000bf64490c7efba098b9ea732" } } ], "extra": [ 1, 223, 65, 50, 234, 87, 88, 0, 185, 162, 230, 45, 158, 196, 206, 206, 166, 133, 219, 4, 151, 171, 197, 47, 95, 155, 187, 151, 151, 199, 101, 109, 77, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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