Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 589be252d0632d93b7e889ef352089d2756cedbc120299aca2c3a9269e95c0bc

Tx prefix hash: dbc6b634395874176cb5e409e9fc2f8401f6b4897948c6f5e849f2655f8be215
Tx public key: 2a2d3a10eadcc84f7fb3bc9136d6c12a531131ba9795adcdf1b214510c945baf
Timestamp: 1711501891 Timestamp [UCT]: 2024-03-27 01:11:31 Age [y:d:h:m:s]: 01:310:17:39:46
Block: 987121 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 480675 RingCT/type: yes/0
Extra: 012a2d3a10eadcc84f7fb3bc9136d6c12a531131ba9795adcdf1b214510c945baf02110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6e65c48e48dbd771f37866713b94ff896f043b7eadbd464a6da733a8a5baeb66 0.600000000000 1447362 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": 987131, "vin": [ { "gen": { "height": 987121 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6e65c48e48dbd771f37866713b94ff896f043b7eadbd464a6da733a8a5baeb66" } } ], "extra": [ 1, 42, 45, 58, 16, 234, 220, 200, 79, 127, 179, 188, 145, 54, 214, 193, 42, 83, 17, 49, 186, 151, 149, 173, 205, 241, 178, 20, 81, 12, 148, 91, 175, 2, 17, 0, 0, 0, 8, 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