Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3c8c81a7ffb43fda0ce58019cc125cd8cd019f4abc00a97d189a4577b90497e

Tx prefix hash: d7d3be20786de944e0525e7e1d2b01b554453b272d92640fdeb03ace75daedd0
Tx public key: cd036ccd5a96db80e9e7b430bce3e439c2c974ee6d4dc8ceaa604a362945c574
Timestamp: 1723013297 Timestamp [UCT]: 2024-08-07 06:48:17 Age [y:d:h:m:s]: 01:104:15:56:44
Block: 1082531 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 333297 RingCT/type: yes/0
Extra: 01cd036ccd5a96db80e9e7b430bce3e439c2c974ee6d4dc8ceaa604a362945c57402110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 058a8fc060578c6f64925d1208ee98c84e1781dc5887f0693969dfe9571b82b3 0.600000000000 1556360 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": 1082541, "vin": [ { "gen": { "height": 1082531 } } ], "vout": [ { "amount": 600000000, "target": { "key": "058a8fc060578c6f64925d1208ee98c84e1781dc5887f0693969dfe9571b82b3" } } ], "extra": [ 1, 205, 3, 108, 205, 90, 150, 219, 128, 233, 231, 180, 48, 188, 227, 228, 57, 194, 201, 116, 238, 109, 77, 200, 206, 170, 96, 74, 54, 41, 69, 197, 116, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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