Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df0497dfbaa3eef05cf97ab40530829fe862ef32238a793c23f2833d7074132e

Tx prefix hash: de973f4f43e542a44935b6617e75ecd2ea359815700e284c106192ea5ad1c9b0
Tx public key: af4931dd56a3d43537c88e9de91fe46aea9dc548d64b8f85f5d4ff766de48151
Timestamp: 1693161074 Timestamp [UCT]: 2023-08-27 18:31:14 Age [y:d:h:m:s]: 01:148:15:09:50
Block: 835214 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 367556 RingCT/type: yes/0
Extra: 01af4931dd56a3d43537c88e9de91fe46aea9dc548d64b8f85f5d4ff766de4815102110000000175e3f0e9000000000000000000

1 output(s) for total of 1.048550574000 dcy

stealth address amount amount idx
00: 6826cfc3e7bcd44b3fce742bbf3f8d295740ce8d01c4f2de5a54134bb110a673 1.048550574000 1287754 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": 835224, "vin": [ { "gen": { "height": 835214 } } ], "vout": [ { "amount": 1048550574, "target": { "key": "6826cfc3e7bcd44b3fce742bbf3f8d295740ce8d01c4f2de5a54134bb110a673" } } ], "extra": [ 1, 175, 73, 49, 221, 86, 163, 212, 53, 55, 200, 142, 157, 233, 31, 228, 106, 234, 157, 197, 72, 214, 75, 143, 133, 245, 212, 255, 118, 109, 228, 129, 81, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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