Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c09362b5572356af8c2ee7196a68ea89e5eb34437b43edaf46056242948b596

Tx prefix hash: e45527a16717fd935186f2bbbd2fa4e3b94b1412d7396edbf510bbcc7614f2b6
Tx public key: aa15e1c2f015044a0c7ac6780bcd85d29b29711631eb52609b4c3687e55179bd
Timestamp: 1695970785 Timestamp [UCT]: 2023-09-29 06:59:45 Age [y:d:h:m:s]: 01:194:07:25:52
Block: 858544 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 399929 RingCT/type: yes/0
Extra: 01aa15e1c2f015044a0c7ac6780bcd85d29b29711631eb52609b4c3687e55179bd021100000001faf35c9c000000000000000000

1 output(s) for total of 0.877581326000 dcy

stealth address amount amount idx
00: 8abd4a06d85f85e751becea4fc8e2a8f636dd89efdab6ae540c3bfb7f7a2da69 0.877581326000 1312726 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": 858554, "vin": [ { "gen": { "height": 858544 } } ], "vout": [ { "amount": 877581326, "target": { "key": "8abd4a06d85f85e751becea4fc8e2a8f636dd89efdab6ae540c3bfb7f7a2da69" } } ], "extra": [ 1, 170, 21, 225, 194, 240, 21, 4, 74, 12, 122, 198, 120, 11, 205, 133, 210, 155, 41, 113, 22, 49, 235, 82, 96, 155, 76, 54, 135, 229, 81, 121, 189, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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