Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e93af2fb4421fbd477a94aed7b5725e79eef0006276410197c0ffb936401776

Tx prefix hash: d1d1bd5e84736b4b4b0f47c8ad3f28f83488baf0eb0b1a147046f3fba5c1b449
Tx public key: f508e614b8bf507f118d4f9223d8c477d8568f4c5b144f8794c4c2aa1a5c9e1a
Timestamp: 1730836414 Timestamp [UCT]: 2024-11-05 19:53:34 Age [y:d:h:m:s]: 00:018:09:48:02
Block: 1147309 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 13174 RingCT/type: yes/0
Extra: 01f508e614b8bf507f118d4f9223d8c477d8568f4c5b144f8794c4c2aa1a5c9e1a021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cf655df802854874b3a14bf93789df99c876649f144163d56b8d27e9361385e7 0.600000000000 1632004 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": 1147319, "vin": [ { "gen": { "height": 1147309 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf655df802854874b3a14bf93789df99c876649f144163d56b8d27e9361385e7" } } ], "extra": [ 1, 245, 8, 230, 20, 184, 191, 80, 127, 17, 141, 79, 146, 35, 216, 196, 119, 216, 86, 143, 76, 91, 20, 79, 135, 148, 196, 194, 170, 26, 92, 158, 26, 2, 17, 0, 0, 0, 4, 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