Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a806c501313751dd819f594ff124d4f67638141ebb0e021671e85e7a7978d6b1

Tx prefix hash: a70c5a184627487d9341d5af4d91f4fdc903b82c3cee9ab0232f20da80f2ec6a
Tx public key: 49c89ad02ec4d6dbc671998434c58f2c67c76c2e13681cd3ea1b73be932a23d2
Timestamp: 1711269304 Timestamp [UCT]: 2024-03-24 08:35:04 Age [y:d:h:m:s]: 01:051:17:12:33
Block: 985195 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297937 RingCT/type: yes/0
Extra: 0149c89ad02ec4d6dbc671998434c58f2c67c76c2e13681cd3ea1b73be932a23d20211000000010424019c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f347b314152652140346856f5f1d2f2c9946209cfe1ad6f1c2f62b3bb821fdb7 0.600000000000 1445404 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": 985205, "vin": [ { "gen": { "height": 985195 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f347b314152652140346856f5f1d2f2c9946209cfe1ad6f1c2f62b3bb821fdb7" } } ], "extra": [ 1, 73, 200, 154, 208, 46, 196, 214, 219, 198, 113, 153, 132, 52, 197, 143, 44, 103, 199, 108, 46, 19, 104, 28, 211, 234, 27, 115, 190, 147, 42, 35, 210, 2, 17, 0, 0, 0, 1, 4, 36, 1, 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