Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d901db7a59101a64887eb81a6832fb12fdb1dcf270c6a14ba3387f262f21cc39

Tx prefix hash: 72b89836b3b83962afeb2a18e27d86dd570297d2b8741b5208c92d6beeb6a381
Tx public key: 99d8e242823eb69f3f79efd4a5d02afe4b21c257bc6510a844ee7249739680e5
Timestamp: 1711585964 Timestamp [UCT]: 2024-03-28 00:32:44 Age [y:d:h:m:s]: 01:028:02:13:16
Block: 987813 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281049 RingCT/type: yes/0
Extra: 0199d8e242823eb69f3f79efd4a5d02afe4b21c257bc6510a844ee7249739680e50211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ac04a265956c036e67dbb18e8417465ac2c7c346df7c76f4b0ca7871a29a0dc9 0.600000000000 1448072 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": 987823, "vin": [ { "gen": { "height": 987813 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ac04a265956c036e67dbb18e8417465ac2c7c346df7c76f4b0ca7871a29a0dc9" } } ], "extra": [ 1, 153, 216, 226, 66, 130, 62, 182, 159, 63, 121, 239, 212, 165, 208, 42, 254, 75, 33, 194, 87, 188, 101, 16, 168, 68, 238, 114, 73, 115, 150, 128, 229, 2, 17, 0, 0, 0, 9, 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