Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 307722b223c6e02a309626a6204952d032467cb2c8dc571539399e629ea2c337

Tx prefix hash: 7d01cd8a127920a321743e13af863bc5adc430e517ab16c0516b3d1ecabc8dd0
Tx public key: 7efc8cdc5912473cc6ecbf8c1b5971f2eb6845e37a1747ac8fd34f52606e027a
Timestamp: 1734265042 Timestamp [UCT]: 2024-12-15 12:17:22 Age [y:d:h:m:s]: 00:107:20:49:43
Block: 1175732 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 76852 RingCT/type: yes/0
Extra: 017efc8cdc5912473cc6ecbf8c1b5971f2eb6845e37a1747ac8fd34f52606e027a0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0296aba51c4ab0a9245c2748049f5f9deb0e8e76a19637796f9f7eb141e84761 0.600000000000 1662055 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": 1175742, "vin": [ { "gen": { "height": 1175732 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0296aba51c4ab0a9245c2748049f5f9deb0e8e76a19637796f9f7eb141e84761" } } ], "extra": [ 1, 126, 252, 140, 220, 89, 18, 71, 60, 198, 236, 191, 140, 27, 89, 113, 242, 235, 104, 69, 227, 122, 23, 71, 172, 143, 211, 79, 82, 96, 110, 2, 122, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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