Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35256828e357251445e3fca9bd1341660f212b808b55f8b38cbc8c9aea73aa73

Tx prefix hash: a0b714432cbe3c8da6f3def1f4df38d2b7cd2eda8c8039a49b4f7fd0e9a02016
Tx public key: 3aee12cd6969f814dc0a1738530d060a66640f6e75ce8bf98171e82922e69c97
Timestamp: 1703380884 Timestamp [UCT]: 2023-12-24 01:21:24 Age [y:d:h:m:s]: 01:027:01:58:25
Block: 919771 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280664 RingCT/type: yes/0
Extra: 013aee12cd6969f814dc0a1738530d060a66640f6e75ce8bf98171e82922e69c970211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 25ec16e020651724d9ba3765e78be412b9c581fcf1de2462cecdba81dea858b4 0.600000000000 1377449 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": 919781, "vin": [ { "gen": { "height": 919771 } } ], "vout": [ { "amount": 600000000, "target": { "key": "25ec16e020651724d9ba3765e78be412b9c581fcf1de2462cecdba81dea858b4" } } ], "extra": [ 1, 58, 238, 18, 205, 105, 105, 248, 20, 220, 10, 23, 56, 83, 13, 6, 10, 102, 100, 15, 110, 117, 206, 139, 249, 129, 113, 232, 41, 34, 230, 156, 151, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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