Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a369b16e1481f68485d20e9cd5216fd96cd9c1ce3591e4587d284950ec6d581

Tx prefix hash: 3f56fc7a03b56305534b25b30d9ce655b38288e9df64bb84025cedbe2d2e1255
Tx public key: a2dc26061dae5fc5df2ca660574ed62dcacd37c1640d1242a0ae2288ff337ce9
Timestamp: 1699243306 Timestamp [UCT]: 2023-11-06 04:01:46 Age [y:d:h:m:s]: 01:191:02:20:05
Block: 885465 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 397811 RingCT/type: yes/0
Extra: 01a2dc26061dae5fc5df2ca660574ed62dcacd37c1640d1242a0ae2288ff337ce9021100000008faf35c9c000000000000000000

1 output(s) for total of 0.714639284000 dcy

stealth address amount amount idx
00: c794d26ec105b7d4e5a530f6f15c5689ad9aed1001a475b43cf0c2784ec12707 0.714639284000 1341240 of 0

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": 885475, "vin": [ { "gen": { "height": 885465 } } ], "vout": [ { "amount": 714639284, "target": { "key": "c794d26ec105b7d4e5a530f6f15c5689ad9aed1001a475b43cf0c2784ec12707" } } ], "extra": [ 1, 162, 220, 38, 6, 29, 174, 95, 197, 223, 44, 166, 96, 87, 78, 214, 45, 202, 205, 55, 193, 100, 13, 18, 66, 160, 174, 34, 136, 255, 51, 124, 233, 2, 17, 0, 0, 0, 8, 250, 243, 92, 156, 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