Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c28266e941cc9508c33c4deb56909541555c88bd1f2dd0787e662d68f4009a69

Tx prefix hash: 88654726eca86356c0f64d2dd552838c7cc9e61e52e65e1f5a8d9e00a7b9bf9f
Tx public key: fd053cbcc5320b89f5c3d8baeccf18c813b3a862a661483a6b82c91177fb3872
Timestamp: 1733693985 Timestamp [UCT]: 2024-12-08 21:39:45 Age [y:d:h:m:s]: 00:126:20:48:26
Block: 1171003 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 90453 RingCT/type: yes/0
Extra: 01fd053cbcc5320b89f5c3d8baeccf18c813b3a862a661483a6b82c91177fb3872021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 59cafb48dd25495cebaba4de972363ad6200778f2317d3e4fed51e3d4d12d14a 0.600000000000 1656738 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": 1171013, "vin": [ { "gen": { "height": 1171003 } } ], "vout": [ { "amount": 600000000, "target": { "key": "59cafb48dd25495cebaba4de972363ad6200778f2317d3e4fed51e3d4d12d14a" } } ], "extra": [ 1, 253, 5, 60, 188, 197, 50, 11, 137, 245, 195, 216, 186, 236, 207, 24, 200, 19, 179, 168, 98, 166, 97, 72, 58, 107, 130, 201, 17, 119, 251, 56, 114, 2, 17, 0, 0, 0, 7, 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