Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44864f3d679f535bd5c2888492f9754e10e6b3ea33592df7657ca2c624e86668

Tx prefix hash: 3df95b81bf18af3a20cc534a33eee028f94cc4ccc586c3412cd303491c103046
Tx public key: 4ea5bc6b37da9b8ed9ececc4d2177cb5e9f91281fb60b71f912152049cc2c1a6
Timestamp: 1738303217 Timestamp [UCT]: 2025-01-31 06:00:17 Age [y:d:h:m:s]: 00:042:06:37:52
Block: 1208882 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 30250 RingCT/type: yes/0
Extra: 014ea5bc6b37da9b8ed9ececc4d2177cb5e9f91281fb60b71f912152049cc2c1a60211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b5514f2403257a04a1e725ead85198ee9d866dc601b798842dbce509049f0f52 0.600000000000 1695617 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": 1208892, "vin": [ { "gen": { "height": 1208882 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b5514f2403257a04a1e725ead85198ee9d866dc601b798842dbce509049f0f52" } } ], "extra": [ 1, 78, 165, 188, 107, 55, 218, 155, 142, 217, 236, 236, 196, 210, 23, 124, 181, 233, 249, 18, 129, 251, 96, 183, 31, 145, 33, 82, 4, 156, 194, 193, 166, 2, 17, 0, 0, 0, 5, 31, 10, 83, 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