Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f77159de5704f64e13c91a2d6fba7b509afc9faab5990c4a500511d0b855226

Tx prefix hash: 801b09f866f6c172e2d393d68ee175d1d3ecf604a489bdbf8299309d24288c15
Tx public key: 04514c1636e34a19e705946735b0284c4ef042912f6ee2d02d56b03373d815d3
Timestamp: 1733943778 Timestamp [UCT]: 2024-12-11 19:02:58 Age [y:d:h:m:s]: 00:109:17:37:50
Block: 1173068 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78205 RingCT/type: yes/0
Extra: 0104514c1636e34a19e705946735b0284c4ef042912f6ee2d02d56b03373d815d30211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e20e1b80d5b8019be59a86407ae9bfe2f83f9110ee5a43f335be081f726ac3ad 0.600000000000 1659045 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": 1173078, "vin": [ { "gen": { "height": 1173068 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e20e1b80d5b8019be59a86407ae9bfe2f83f9110ee5a43f335be081f726ac3ad" } } ], "extra": [ 1, 4, 81, 76, 22, 54, 227, 74, 25, 231, 5, 148, 103, 53, 176, 40, 76, 78, 240, 66, 145, 47, 110, 226, 208, 45, 86, 176, 51, 115, 216, 21, 211, 2, 17, 0, 0, 0, 5, 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