Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3330630b8c21deca90a8714bbcecd0d4d5ba7302bfb7a2a44aa0abb5b1e1c1c0

Tx prefix hash: 6c341da051b0f528df95c67772293781813cfd55af242d0ffcf1352bf010b304
Tx public key: ee94543a7e4012783e6fc7bf8a5e768b567cfbbf538a94c14b9a6baded9c2a41
Timestamp: 1727632930 Timestamp [UCT]: 2024-09-29 18:02:10 Age [y:d:h:m:s]: 00:220:07:50:05
Block: 1120839 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157287 RingCT/type: yes/0
Extra: 01ee94543a7e4012783e6fc7bf8a5e768b567cfbbf538a94c14b9a6baded9c2a4102110000000a91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2134d9956a885dfd92cd3e69e44e3d87f416d02f66588456379ccf369e4674f9 0.600000000000 1602898 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": 1120849, "vin": [ { "gen": { "height": 1120839 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2134d9956a885dfd92cd3e69e44e3d87f416d02f66588456379ccf369e4674f9" } } ], "extra": [ 1, 238, 148, 84, 58, 126, 64, 18, 120, 62, 111, 199, 191, 138, 94, 118, 139, 86, 124, 251, 191, 83, 138, 148, 193, 75, 154, 107, 173, 237, 156, 42, 65, 2, 17, 0, 0, 0, 10, 145, 225, 60, 4, 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