Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 588a232d79b34b4d7fe9a3c536162a963d31cb60c9384f2c79502e5eddc7ef1b

Tx prefix hash: 1ec449ce6759e7994eea80aa730d9cb1bc343e21b434130ba51b497f7bd214a7
Tx public key: 2b306ed0921c6dfcfdc1927d0e3a1815732a50f604f5661b68be8c01e6d1c44d
Timestamp: 1712327391 Timestamp [UCT]: 2024-04-05 14:29:51 Age [y:d:h:m:s]: 00:343:10:08:39
Block: 993918 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 245565 RingCT/type: yes/0
Extra: 012b306ed0921c6dfcfdc1927d0e3a1815732a50f604f5661b68be8c01e6d1c44d02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fdd9a2d75600a05fb321ee5fc11a33e90134f1c2d623e5ac4f935879e6669d10 0.600000000000 1454314 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": 993928, "vin": [ { "gen": { "height": 993918 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fdd9a2d75600a05fb321ee5fc11a33e90134f1c2d623e5ac4f935879e6669d10" } } ], "extra": [ 1, 43, 48, 110, 208, 146, 28, 109, 252, 253, 193, 146, 125, 14, 58, 24, 21, 115, 42, 80, 246, 4, 245, 102, 27, 104, 190, 140, 1, 230, 209, 196, 77, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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