Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b61bb0f03332c7bee156119c9263419fad09f36dc9b0756e01d3e051d5acc936

Tx prefix hash: e50f839645ca1d03b8b8f572fd4454bb71e97431abae49b42401715c6b5670a9
Tx public key: a580c0ef77d0f8d3ebb3399cf34e97026b7d8f2900f439195872a0f41ba57974
Timestamp: 1710910677 Timestamp [UCT]: 2024-03-20 04:57:57 Age [y:d:h:m:s]: 01:260:04:03:21
Block: 982219 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 444671 RingCT/type: yes/0
Extra: 01a580c0ef77d0f8d3ebb3399cf34e97026b7d8f2900f439195872a0f41ba5797402110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fe2235efc0e4dcfb8f60df974de5e3b3fa905c7979b38570b3b3c52055fd4047 0.600000000000 1442324 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": 982229, "vin": [ { "gen": { "height": 982219 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe2235efc0e4dcfb8f60df974de5e3b3fa905c7979b38570b3b3c52055fd4047" } } ], "extra": [ 1, 165, 128, 192, 239, 119, 208, 248, 211, 235, 179, 57, 156, 243, 78, 151, 2, 107, 125, 143, 41, 0, 244, 57, 25, 88, 114, 160, 244, 27, 165, 121, 116, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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