Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93704284e758598e8dfd64a311bb1590e9352d42f0c926c512de50cf19c96192

Tx prefix hash: 081f629db4272b71d1dfc98dbded8c88e6d158e2c6bfa6a0879d3976024ac751
Tx public key: 16cee1807ec93b2d32f3543097966423e41e68a4f5c475c9fa2a2d280c45bb41
Timestamp: 1731834949 Timestamp [UCT]: 2024-11-17 09:15:49 Age [y:d:h:m:s]: 01:073:19:07:47
Block: 1155571 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311081 RingCT/type: yes/0
Extra: 0116cee1807ec93b2d32f3543097966423e41e68a4f5c475c9fa2a2d280c45bb41021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ce5fb8bee9ad5adf04c5623f6c29144006915d754b67cf829fe968070ba21f9 0.600000000000 1641188 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": 1155581, "vin": [ { "gen": { "height": 1155571 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ce5fb8bee9ad5adf04c5623f6c29144006915d754b67cf829fe968070ba21f9" } } ], "extra": [ 1, 22, 206, 225, 128, 126, 201, 59, 45, 50, 243, 84, 48, 151, 150, 100, 35, 228, 30, 104, 164, 245, 196, 117, 201, 250, 42, 45, 40, 12, 69, 187, 65, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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