Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f23d3227f417cac1bdac889a0d0209cc0367241f70fbcb5039db1776e86239b0

Tx prefix hash: cacb6b88b1c331db2438066e9ac966fe07e9f24976677c7a76f957cabf7ffcdc
Tx public key: 250c19bf703d2cff20eea40137e9b07f95c064a76842a0ad44b46b14e289c6f0
Timestamp: 1719784575 Timestamp [UCT]: 2024-06-30 21:56:15 Age [y:d:h:m:s]: 01:131:09:30:54
Block: 1055759 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 352454 RingCT/type: yes/0
Extra: 01250c19bf703d2cff20eea40137e9b07f95c064a76842a0ad44b46b14e289c6f002110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ac49ec83e8200dad9f4e7a844d956d7a22944f3f0c3f29d448565cdd705e1c56 0.600000000000 1526164 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": 1055769, "vin": [ { "gen": { "height": 1055759 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ac49ec83e8200dad9f4e7a844d956d7a22944f3f0c3f29d448565cdd705e1c56" } } ], "extra": [ 1, 37, 12, 25, 191, 112, 61, 44, 255, 32, 238, 164, 1, 55, 233, 176, 127, 149, 192, 100, 167, 104, 66, 160, 173, 68, 180, 107, 20, 226, 137, 198, 240, 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