Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c1fc0c12dce44ff2a170c81bc9100498e5f1effc0a5d3f529521d314fb23e6c4

Tx prefix hash: 700ead6046ff4b9fae533c75311898c59bb6c069eae96dc6e440c998c85611be
Tx public key: 835787b2d66410657f7145a74f9eb75319baeec24eb72a98f4f35bf9784c4cb1
Timestamp: 1712118616 Timestamp [UCT]: 2024-04-03 04:30:16 Age [y:d:h:m:s]: 00:281:00:54:06
Block: 992183 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201203 RingCT/type: yes/0
Extra: 01835787b2d66410657f7145a74f9eb75319baeec24eb72a98f4f35bf9784c4cb10211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a86164cbdcf17947262ee5808c8d79f7b63a63e054c3e560fa793fd9bf470dfc 0.600000000000 1452521 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": 992193, "vin": [ { "gen": { "height": 992183 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a86164cbdcf17947262ee5808c8d79f7b63a63e054c3e560fa793fd9bf470dfc" } } ], "extra": [ 1, 131, 87, 135, 178, 214, 100, 16, 101, 127, 113, 69, 167, 79, 158, 183, 83, 25, 186, 238, 194, 78, 183, 42, 152, 244, 243, 91, 249, 120, 76, 76, 177, 2, 17, 0, 0, 0, 3, 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