Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4dbe66d4ca2124d74ed30f2f7b287eee4e8e2d2e1e91da04be1e3d77334e7b34

Tx prefix hash: 463b3c36ca36b360cb55bf165020fb6810ed0aa9d42a679816d275fae2fc280f
Tx public key: 44dd0ae671d64facf671ae20711cf9bbdcb63600b93282bee5caf2f6ed364145
Timestamp: 1713920325 Timestamp [UCT]: 2024-04-24 00:58:45 Age [y:d:h:m:s]: 00:205:10:52:33
Block: 1007148 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147077 RingCT/type: yes/0
Extra: 0144dd0ae671d64facf671ae20711cf9bbdcb63600b93282bee5caf2f6ed36414502110000000b7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 05e3c3c32b29e1d6f1eeb2c53d30ae8853442761c6a42338eaf6246be68e9a83 0.600000000000 1468398 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": 1007158, "vin": [ { "gen": { "height": 1007148 } } ], "vout": [ { "amount": 600000000, "target": { "key": "05e3c3c32b29e1d6f1eeb2c53d30ae8853442761c6a42338eaf6246be68e9a83" } } ], "extra": [ 1, 68, 221, 10, 230, 113, 214, 79, 172, 246, 113, 174, 32, 113, 28, 249, 187, 220, 182, 54, 0, 185, 50, 130, 190, 229, 202, 242, 246, 237, 54, 65, 69, 2, 17, 0, 0, 0, 11, 122, 156, 244, 199, 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