Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d5502288d4c9061c9c55e9c5918c692257ef85f627e8cf3af11e726f00afaeb

Tx prefix hash: 45cb03380e869451e7776d12abf4110acf7ee05a4fa5f72d106922d51e548a9c
Tx public key: f4b231ba00f54ddd1314de0c037dce04d9435f3f4673cffd05b426289a5363af
Timestamp: 1609279202 Timestamp [UCT]: 2020-12-29 22:00:02 Age [y:d:h:m:s]: 04:137:00:11:57
Block: 171679 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1111359 RingCT/type: yes/0
Extra: 01f4b231ba00f54ddd1314de0c037dce04d9435f3f4673cffd05b426289a5363af02110000028527e2517e000000000000000000

1 output(s) for total of 165.636814253000 dcy

stealth address amount amount idx
00: 3e872488f45172a8c44e2ab1dc535327600e37dc7e8953cff0aa4614cc475d68 165.636814253000 323750 of 0

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": 171689, "vin": [ { "gen": { "height": 171679 } } ], "vout": [ { "amount": 165636814253, "target": { "key": "3e872488f45172a8c44e2ab1dc535327600e37dc7e8953cff0aa4614cc475d68" } } ], "extra": [ 1, 244, 178, 49, 186, 0, 245, 77, 221, 19, 20, 222, 12, 3, 125, 206, 4, 217, 67, 95, 63, 70, 115, 207, 253, 5, 180, 38, 40, 154, 83, 99, 175, 2, 17, 0, 0, 2, 133, 39, 226, 81, 126, 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