Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45ed33c8b8ab0ad651a3bf1cdfbb0fc62dbcbfa6aa5d627fd9c41222dc250d0c

Tx prefix hash: 6efa6794bbaae540d2aef922d54e00b57b51b98e4ddcff253f094633bfa442bc
Tx public key: d7afb33674d20e72e60aa96bf44b208d82952ab5a06272ee811d0d7ed3d0182a
Timestamp: 1711714960 Timestamp [UCT]: 2024-03-29 12:22:40 Age [y:d:h:m:s]: 00:230:23:13:04
Block: 988890 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165326 RingCT/type: yes/0
Extra: 01d7afb33674d20e72e60aa96bf44b208d82952ab5a06272ee811d0d7ed3d0182a0211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c70c36a67c4cf4afb20d20a20d3ec67f7a4c4efd5ff1bff2603f222cdbdc21c9 0.600000000000 1449177 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": 988900, "vin": [ { "gen": { "height": 988890 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c70c36a67c4cf4afb20d20a20d3ec67f7a4c4efd5ff1bff2603f222cdbdc21c9" } } ], "extra": [ 1, 215, 175, 179, 54, 116, 210, 14, 114, 230, 10, 169, 107, 244, 75, 32, 141, 130, 149, 42, 181, 160, 98, 114, 238, 129, 29, 13, 126, 211, 208, 24, 42, 2, 17, 0, 0, 0, 6, 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