Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c572ec745a27bb8a748f508c869f787510b238dab74cf63312f8df0a78b90a3

Tx prefix hash: 4d39ca7ce9bb01165302ccf8977dae265e857b0cfd9a55a46a3bd1f830206d03
Tx public key: bbe356fdb8c7de69f9ebf6c7a610dba34316eda2fb7d17c8a79d81deb28405fc
Timestamp: 1701008377 Timestamp [UCT]: 2023-11-26 14:19:37 Age [y:d:h:m:s]: 01:095:08:25:15
Block: 900101 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329283 RingCT/type: yes/0
Extra: 01bbe356fdb8c7de69f9ebf6c7a610dba34316eda2fb7d17c8a79d81deb28405fc02110000000475e3f0e9000000000000000000

1 output(s) for total of 0.639133704000 dcy

stealth address amount amount idx
00: de3a3ae56ac1756beda3457cd16ed9dccb7f805e36045153159825231b70d46a 0.639133704000 1356578 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": 900111, "vin": [ { "gen": { "height": 900101 } } ], "vout": [ { "amount": 639133704, "target": { "key": "de3a3ae56ac1756beda3457cd16ed9dccb7f805e36045153159825231b70d46a" } } ], "extra": [ 1, 187, 227, 86, 253, 184, 199, 222, 105, 249, 235, 246, 199, 166, 16, 219, 163, 67, 22, 237, 162, 251, 125, 23, 200, 167, 157, 129, 222, 178, 132, 5, 252, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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