Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 95b5a438c1089d8cb68f9b59de160bd2cde2524b8851d295f1d024c07927b67b

Tx prefix hash: 84943f404824d6e7942fd6d8e90233f7acf393ef63d0173975116485e2749eb4
Tx public key: f64fb842d0cfc5d5e88462a12c96dc883598dbeb3690fee7226ba3fcf7be69e4
Timestamp: 1720646366 Timestamp [UCT]: 2024-07-10 21:19:26 Age [y:d:h:m:s]: 00:265:21:52:00
Block: 1062917 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189972 RingCT/type: yes/0
Extra: 01f64fb842d0cfc5d5e88462a12c96dc883598dbeb3690fee7226ba3fcf7be69e402110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 609dcb5c8b94f8998faec0bcb77f1201fdc33a282bd8456ef161ba85eaa11342 0.600000000000 1533428 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": 1062927, "vin": [ { "gen": { "height": 1062917 } } ], "vout": [ { "amount": 600000000, "target": { "key": "609dcb5c8b94f8998faec0bcb77f1201fdc33a282bd8456ef161ba85eaa11342" } } ], "extra": [ 1, 246, 79, 184, 66, 208, 207, 197, 213, 232, 132, 98, 161, 44, 150, 220, 136, 53, 152, 219, 235, 54, 144, 254, 231, 34, 107, 163, 252, 247, 190, 105, 228, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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