Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 557c94af8944da657de83485080986dafb2496225dca8b3ac3e16e6f3e7722e2

Tx prefix hash: 258e5c2fabdf7cde4c008de585804b31c9f940d20830f57a21266c849a84928b
Tx public key: b394768f7b89b97f9b256417757b946fb24d8d4646069a88d2b9526b1bd1e433
Timestamp: 1714777624 Timestamp [UCT]: 2024-05-03 23:07:04 Age [y:d:h:m:s]: 00:348:06:15:34
Block: 1014267 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248934 RingCT/type: yes/0
Extra: 01b394768f7b89b97f9b256417757b946fb24d8d4646069a88d2b9526b1bd1e4330211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a19458c62512be5e7fd8b06394a845de1d1791d2eabfd35bdda938bda6821fb5 0.600000000000 1477304 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": 1014277, "vin": [ { "gen": { "height": 1014267 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a19458c62512be5e7fd8b06394a845de1d1791d2eabfd35bdda938bda6821fb5" } } ], "extra": [ 1, 179, 148, 118, 143, 123, 137, 185, 127, 155, 37, 100, 23, 117, 123, 148, 111, 178, 77, 141, 70, 70, 6, 154, 136, 210, 185, 82, 107, 27, 209, 228, 51, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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