Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d335994211281e65949e4e13f199ff9a8f16703f740a42810e477df040d7567d

Tx prefix hash: 52061c08d697760b9d70a2cb333f90455b9c5e593f2492d2f3834587f83b35d6
Tx public key: ac07f2b0425c8e3718d73b8d070ba30ba0d0410e82793d884efd79f1cb4d3cfd
Timestamp: 1705104373 Timestamp [UCT]: 2024-01-13 00:06:13 Age [y:d:h:m:s]: 01:081:00:18:27
Block: 934042 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318992 RingCT/type: yes/0
Extra: 01ac07f2b0425c8e3718d73b8d070ba30ba0d0410e82793d884efd79f1cb4d3cfd02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3153f35d672c9989591113c1057c7eb77e1064750b57a9f9cf10ac230621a960 0.600000000000 1392028 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": 934052, "vin": [ { "gen": { "height": 934042 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3153f35d672c9989591113c1057c7eb77e1064750b57a9f9cf10ac230621a960" } } ], "extra": [ 1, 172, 7, 242, 176, 66, 92, 142, 55, 24, 215, 59, 141, 7, 11, 163, 11, 160, 208, 65, 14, 130, 121, 61, 136, 78, 253, 121, 241, 203, 77, 60, 253, 2, 17, 0, 0, 0, 4, 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