Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f37eefe7811daf7d199f1c6df612573bfa44a1e9d6e9282556eefd7edb68c883

Tx prefix hash: 26c1db12229a67dc60cd65a806077d919cdfbf242ecd9b47f8f4f16c344da9ad
Tx public key: bb09d7f8adca1df0d6f0bfdcee24f1aa2e394d5db0a8f0eeb42db0b94d096610
Timestamp: 1729065148 Timestamp [UCT]: 2024-10-16 07:52:28 Age [y:d:h:m:s]: 00:220:20:54:29
Block: 1132728 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157659 RingCT/type: yes/0
Extra: 01bb09d7f8adca1df0d6f0bfdcee24f1aa2e394d5db0a8f0eeb42db0b94d0966100211000000073cd0fc06000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e685bb0ea053d88cb6fbbbd962787034e08b6d4f35cf62e1d0be5009d7e3cbe 0.600000000000 1615711 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": 1132738, "vin": [ { "gen": { "height": 1132728 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e685bb0ea053d88cb6fbbbd962787034e08b6d4f35cf62e1d0be5009d7e3cbe" } } ], "extra": [ 1, 187, 9, 215, 248, 173, 202, 29, 240, 214, 240, 191, 220, 238, 36, 241, 170, 46, 57, 77, 93, 176, 168, 240, 238, 180, 45, 176, 185, 77, 9, 102, 16, 2, 17, 0, 0, 0, 7, 60, 208, 252, 6, 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