Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa157f37a394c3d70ba9014595255a1956469861b85c2724a7f9c04aad5e7516

Tx prefix hash: 39ef36e6780de3295f7eed9be479462859f312d28cb25f4e475af3e187d26f60
Tx public key: 1c6bdc22a6a3bb1578da67ea31a35e4734d8b490078f0ea7287c1b684d2892fa
Timestamp: 1707095734 Timestamp [UCT]: 2024-02-05 01:15:34 Age [y:d:h:m:s]: 01:051:12:01:43
Block: 950562 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297853 RingCT/type: yes/0
Extra: 011c6bdc22a6a3bb1578da67ea31a35e4734d8b490078f0ea7287c1b684d2892fa02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 807c68bde999da3dae56f4183aeb04a3d09b86070d3abd50e6b6c18f5fc07c13 0.600000000000 1409200 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": 950572, "vin": [ { "gen": { "height": 950562 } } ], "vout": [ { "amount": 600000000, "target": { "key": "807c68bde999da3dae56f4183aeb04a3d09b86070d3abd50e6b6c18f5fc07c13" } } ], "extra": [ 1, 28, 107, 220, 34, 166, 163, 187, 21, 120, 218, 103, 234, 49, 163, 94, 71, 52, 216, 180, 144, 7, 143, 14, 167, 40, 124, 27, 104, 77, 40, 146, 250, 2, 17, 0, 0, 0, 2, 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