Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ab6d363cba51001b011550cd56b6c3c5e1468282e4a2d857b6faff5adb023c7

Tx prefix hash: 806a4092f9d7fbe263a8f5edc2046a7dc37ef5d83c06dcaaf1ff502bae470fbc
Tx public key: 85e88316983780a6a75d343dadeffd55d5fa0d1fcac9dc8c585b110f59b24969
Timestamp: 1705685298 Timestamp [UCT]: 2024-01-19 17:28:18 Age [y:d:h:m:s]: 00:300:01:33:47
Block: 938849 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214878 RingCT/type: yes/0
Extra: 0185e88316983780a6a75d343dadeffd55d5fa0d1fcac9dc8c585b110f59b2496902110000000179bda3be000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3be987837fc87b7c1d81de4820580c0f4bf49b1be57418434abb7cc404b83aa8 0.600000000000 1396931 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": 938859, "vin": [ { "gen": { "height": 938849 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3be987837fc87b7c1d81de4820580c0f4bf49b1be57418434abb7cc404b83aa8" } } ], "extra": [ 1, 133, 232, 131, 22, 152, 55, 128, 166, 167, 93, 52, 61, 173, 239, 253, 85, 213, 250, 13, 31, 202, 201, 220, 140, 88, 91, 17, 15, 89, 178, 73, 105, 2, 17, 0, 0, 0, 1, 121, 189, 163, 190, 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