Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37c6f434bcddd72df6c2640b62341200c7e50c8d54fe7b6ccf499d19e1e14906

Tx prefix hash: b26f7a974b27e24f958a4f0dce123014218c706fc0ee78344d0f8e089cae0782
Tx public key: a14f608d475f56ec14facb7e511e2e5159bad8facde905064a98e234c6251cef
Timestamp: 1733302441 Timestamp [UCT]: 2024-12-04 08:54:01 Age [y:d:h:m:s]: 00:101:20:28:07
Block: 1167733 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72604 RingCT/type: yes/0
Extra: 01a14f608d475f56ec14facb7e511e2e5159bad8facde905064a98e234c6251cef0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f842f287f04c412fd20ccdd1ff31dc7aceb614f19f0d6e2c328113444d6a73ab 0.600000000000 1653434 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": 1167743, "vin": [ { "gen": { "height": 1167733 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f842f287f04c412fd20ccdd1ff31dc7aceb614f19f0d6e2c328113444d6a73ab" } } ], "extra": [ 1, 161, 79, 96, 141, 71, 95, 86, 236, 20, 250, 203, 126, 81, 30, 46, 81, 89, 186, 216, 250, 205, 233, 5, 6, 74, 152, 226, 52, 198, 37, 28, 239, 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