Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b598ef0c042d52ce453f6743c5ac7a2cf436f4aa7d0b9986345830b402f7805

Tx prefix hash: 2c67e408d82d2a068e19cf15c34af6e71171722157caad89ac93f833f3af5fb9
Tx public key: 6d86e6082d8111ba371b035ba7c2628221c9a5559d4e2313ba891d84e74df27d
Timestamp: 1709270654 Timestamp [UCT]: 2024-03-01 05:24:14 Age [y:d:h:m:s]: 01:089:22:24:33
Block: 968614 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325319 RingCT/type: yes/0
Extra: 016d86e6082d8111ba371b035ba7c2628221c9a5559d4e2313ba891d84e74df27d02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0346b6969cd4621486bb6c21254f69fc24a7243d30718a36661b7fa22fecfdc0 0.600000000000 1428431 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": 968624, "vin": [ { "gen": { "height": 968614 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0346b6969cd4621486bb6c21254f69fc24a7243d30718a36661b7fa22fecfdc0" } } ], "extra": [ 1, 109, 134, 230, 8, 45, 129, 17, 186, 55, 27, 3, 91, 167, 194, 98, 130, 33, 201, 165, 85, 157, 78, 35, 19, 186, 137, 29, 132, 231, 77, 242, 125, 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