Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1c436f13e32a86dc54f3ce345c513727c59f7f4e019059bb78a2b6babeab3df

Tx prefix hash: be68adc141415a776b89742cb29be9e09b236ec18943981b0a11c17a598f3354
Tx public key: bae24698a56bee09a40806dc8e9a7b3afb0a5890fa7b953df6e6991d53bbaa21
Timestamp: 1726851815 Timestamp [UCT]: 2024-09-20 17:03:35 Age [y:d:h:m:s]: 00:193:08:47:12
Block: 1114360 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 138004 RingCT/type: yes/0
Extra: 01bae24698a56bee09a40806dc8e9a7b3afb0a5890fa7b953df6e6991d53bbaa21021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 54a1ae21b7222e36734e7ffb595671abe0424bac2ac78ff0b24d4e2259740d8f 0.600000000000 1594161 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": 1114370, "vin": [ { "gen": { "height": 1114360 } } ], "vout": [ { "amount": 600000000, "target": { "key": "54a1ae21b7222e36734e7ffb595671abe0424bac2ac78ff0b24d4e2259740d8f" } } ], "extra": [ 1, 186, 226, 70, 152, 165, 107, 238, 9, 164, 8, 6, 220, 142, 154, 123, 58, 251, 10, 88, 144, 250, 123, 149, 61, 246, 230, 153, 29, 83, 187, 170, 33, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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