Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b61585f56d7d562ef47719e1833811b6f56d4a57e6a1e977507d7031dd263133

Tx prefix hash: a9065743c066d2a43b50994108b5b622299ba688f1fbb0255220c9e3585032e5
Tx public key: afbf0fd2b892e4e471a7b0af42ec20148c63b208bf5f2e26e70d00c6a04c594b
Timestamp: 1707676167 Timestamp [UCT]: 2024-02-11 18:29:27 Age [y:d:h:m:s]: 00:333:12:50:12
Block: 955382 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238771 RingCT/type: yes/0
Extra: 01afbf0fd2b892e4e471a7b0af42ec20148c63b208bf5f2e26e70d00c6a04c594b0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e3c1297613f19950e35ea790b3b244acdcaeda8687620ae6618c2a8e18d4c054 0.600000000000 1414670 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": 955392, "vin": [ { "gen": { "height": 955382 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e3c1297613f19950e35ea790b3b244acdcaeda8687620ae6618c2a8e18d4c054" } } ], "extra": [ 1, 175, 191, 15, 210, 184, 146, 228, 228, 113, 167, 176, 175, 66, 236, 32, 20, 140, 99, 178, 8, 191, 95, 46, 38, 231, 13, 0, 198, 160, 76, 89, 75, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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