Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2342962c67af0bf69fb510ec8263886da4fad1709709644e57a658b1f7455853

Tx prefix hash: 6ee8aa12f18a6aa8571e46bd0d1f12b8370c6becfdff7434b6e0f4f980b57399
Tx public key: d04531d73c1ae3a3d333c2e8a053c04373add106d053139d8371bff1db66f113
Timestamp: 1672803789 Timestamp [UCT]: 2023-01-04 03:43:09 Age [y:d:h:m:s]: 02:091:08:52:54
Block: 667150 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 586977 RingCT/type: yes/0
Extra: 01d04531d73c1ae3a3d333c2e8a053c04373add106d053139d8371bff1db66f11302110000000152542ceb000000000000000000

1 output(s) for total of 3.779680276000 dcy

stealth address amount amount idx
00: c1895188754e16d2f31e65c7bd4001dee191a578bd87dae3ccdbc9962e31d0e5 3.779680276000 1108315 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": 667160, "vin": [ { "gen": { "height": 667150 } } ], "vout": [ { "amount": 3779680276, "target": { "key": "c1895188754e16d2f31e65c7bd4001dee191a578bd87dae3ccdbc9962e31d0e5" } } ], "extra": [ 1, 208, 69, 49, 215, 60, 26, 227, 163, 211, 51, 194, 232, 160, 83, 192, 67, 115, 173, 209, 6, 208, 83, 19, 157, 131, 113, 191, 241, 219, 102, 241, 19, 2, 17, 0, 0, 0, 1, 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