Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ab4b28757699bc68b3026b2331ee4da0e6a0d700d2fa4a088b8fe509ae9824f

Tx prefix hash: 2ac7bf454a397cccb2bcde37c6c002437b1af967202eb4babbaa8e232ad8cf1b
Tx public key: e70c37a9ba46d3ccc44d242786d5da093f4f135acaf0740a06ca8d75dd4deae8
Timestamp: 1702764737 Timestamp [UCT]: 2023-12-16 22:12:17 Age [y:d:h:m:s]: 01:034:06:53:54
Block: 914664 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285821 RingCT/type: yes/0
Extra: 01e70c37a9ba46d3ccc44d242786d5da093f4f135acaf0740a06ca8d75dd4deae8021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 80a0527ceddde353598e426c796ba117a9efb836f1576e8f0695c5c3a6d9f230 0.600000000000 1372014 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": 914674, "vin": [ { "gen": { "height": 914664 } } ], "vout": [ { "amount": 600000000, "target": { "key": "80a0527ceddde353598e426c796ba117a9efb836f1576e8f0695c5c3a6d9f230" } } ], "extra": [ 1, 231, 12, 55, 169, 186, 70, 211, 204, 196, 77, 36, 39, 134, 213, 218, 9, 63, 79, 19, 90, 202, 240, 116, 10, 6, 202, 141, 117, 221, 77, 234, 232, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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