Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 475d561785c1d5d82c7b33343a2590521a94b42284f951636c803caeca074e65

Tx prefix hash: a9aa93985e3c03d5f04fbefaddeecdf4147215ea9c57a4c0298bdd38e45ecc6f
Tx public key: c486f0a6126e77cd65b04526494259dea40216c1ebe9feb1e81c734674f366aa
Timestamp: 1724534970 Timestamp [UCT]: 2024-08-24 21:29:30 Age [y:d:h:m:s]: 00:181:18:42:54
Block: 1095174 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 129715 RingCT/type: yes/0
Extra: 01c486f0a6126e77cd65b04526494259dea40216c1ebe9feb1e81c734674f366aa021100000002e337358e000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2ffeb4b1883be69fb0ec630fc7b271befd8e8a93517a7a69084fc669957178be 0.600000000000 1570323 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": 1095184, "vin": [ { "gen": { "height": 1095174 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ffeb4b1883be69fb0ec630fc7b271befd8e8a93517a7a69084fc669957178be" } } ], "extra": [ 1, 196, 134, 240, 166, 18, 110, 119, 205, 101, 176, 69, 38, 73, 66, 89, 222, 164, 2, 22, 193, 235, 233, 254, 177, 232, 28, 115, 70, 116, 243, 102, 170, 2, 17, 0, 0, 0, 2, 227, 55, 53, 142, 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