Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: efaf315dac3bea0a6ec4688467d5ed5efa8274f1e95d9f42621ccd16c3e74535

Tx prefix hash: 135906aea09f28a1273dbdaab68a2a2c62f1154306aa1c26852fe07a7cda8888
Tx public key: 90610c9a6a3a8b82ba8b54cf84203b609f618d1ff2dc07afa9d7385d11dae97c
Timestamp: 1673479457 Timestamp [UCT]: 2023-01-11 23:24:17 Age [y:d:h:m:s]: 02:137:22:47:27
Block: 672734 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 620313 RingCT/type: yes/0
Extra: 0190610c9a6a3a8b82ba8b54cf84203b609f618d1ff2dc07afa9d7385d11dae97c0211000000038b7b6602000000000000000000

1 output(s) for total of 3.622037531000 dcy

stealth address amount amount idx
00: 19b9c29548ff53618b034a6ee3437a416c1aa076f9b80b3b541f49308113a1d2 3.622037531000 1114299 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": 672744, "vin": [ { "gen": { "height": 672734 } } ], "vout": [ { "amount": 3622037531, "target": { "key": "19b9c29548ff53618b034a6ee3437a416c1aa076f9b80b3b541f49308113a1d2" } } ], "extra": [ 1, 144, 97, 12, 154, 106, 58, 139, 130, 186, 139, 84, 207, 132, 32, 59, 96, 159, 97, 141, 31, 242, 220, 7, 175, 169, 215, 56, 93, 17, 218, 233, 124, 2, 17, 0, 0, 0, 3, 139, 123, 102, 2, 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