Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d3a51065e6ebadc4524fe40b5096285bc1c85b8ba6ef569a25bba0a16a143f6

Tx prefix hash: 01e92d087bf08698af2c0fed41a5b3f8373c4b6f72c638576316edb97c44c494
Tx public key: e930d12dc4cee96f442978285e87f9f0bd149f492c362578f1618f9c93acb895
Timestamp: 1725251294 Timestamp [UCT]: 2024-09-02 04:28:14 Age [y:d:h:m:s]: 00:245:03:34:03
Block: 1101092 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175071 RingCT/type: yes/0
Extra: 01e930d12dc4cee96f442978285e87f9f0bd149f492c362578f1618f9c93acb89502110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2929a9502ffd3dfb41e1a835e927806cb1564c8fe771fef32d2c8a1e5444de70 0.600000000000 1577073 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": 1101102, "vin": [ { "gen": { "height": 1101092 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2929a9502ffd3dfb41e1a835e927806cb1564c8fe771fef32d2c8a1e5444de70" } } ], "extra": [ 1, 233, 48, 209, 45, 196, 206, 233, 111, 68, 41, 120, 40, 94, 135, 249, 240, 189, 20, 159, 73, 44, 54, 37, 120, 241, 97, 143, 156, 147, 172, 184, 149, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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