Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1884dc8ba9486a66bcf0a8788ec59a6f1a82f81672dfd9a2c56cd411c588d5ae

Tx prefix hash: 4dfb57f1c71e11b0c47f642c061ebdcfd836ec237e7c58919a4ed03112ba8c42
Tx public key: f43bc3b0ebcb51471ec38a20734e46507729fd05d606bcd9e19a8181a38da0c1
Timestamp: 1673208184 Timestamp [UCT]: 2023-01-08 20:03:04 Age [y:d:h:m:s]: 02:070:15:28:38
Block: 670483 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 572191 RingCT/type: yes/0
Extra: 01f43bc3b0ebcb51471ec38a20734e46507729fd05d606bcd9e19a8181a38da0c102110000000352542ceb000000000000000000

1 output(s) for total of 3.684779011000 dcy

stealth address amount amount idx
00: ecf0b89c3d9808d3b80dd1787813bd5084a2765b37760557f3e4e876ebb3ebfc 3.684779011000 1111890 of 0

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": 670493, "vin": [ { "gen": { "height": 670483 } } ], "vout": [ { "amount": 3684779011, "target": { "key": "ecf0b89c3d9808d3b80dd1787813bd5084a2765b37760557f3e4e876ebb3ebfc" } } ], "extra": [ 1, 244, 59, 195, 176, 235, 203, 81, 71, 30, 195, 138, 32, 115, 78, 70, 80, 119, 41, 253, 5, 214, 6, 188, 217, 225, 154, 129, 129, 163, 141, 160, 193, 2, 17, 0, 0, 0, 3, 82, 84, 44, 235, 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